Block device write-verify test.
authoremellor@leeni.uk.xensource.com <emellor@leeni.uk.xensource.com>
Thu, 1 Jun 2006 10:47:00 +0000 (11:47 +0100)
committeremellor@leeni.uk.xensource.com <emellor@leeni.uk.xensource.com>
Thu, 1 Jun 2006 10:47:00 +0000 (11:47 +0100)
commit7218286f5211e3b89a0dea3d368d66d02fd4ef4f
tree66912ed073170ff0e8783c8551ad128699c4f133
parent1a59e1d7a753243f597d30ab43a04e3c315f5a5a
Block device write-verify test.

This test imports a ram disk device as a physical device into a domU.
The domU initialises the ram disk with data from /dev/urandom and
calculates the md5 checksum of the data (using tee as it is written so as to
avoid reading it back from the device which might potentially mask
problems).
The domU is stopped and the md5 checksum of the data on the device is
calculated by dom0.  The test succeeds if the checksums match, indicating
that all the data written by domU was sucessfully committed to the
device.

This patch also enables tee in BusyBox on the ramdisk and increments the
xm-test version number to 0.8.0.

The patch also installs the block-integrity tests in the default test
set so they get executed.

Signed-off-by: Harry Butterworth <butterwo@uk.ibm.com>
Signed-off-by: Ewan Mellor <ewan@xensource.com>
tools/xm-test/configure.ac
tools/xm-test/grouptest/default
tools/xm-test/ramdisk/configs/busybox
tools/xm-test/tests/block-integrity/02_block_device_write_verify.py [new file with mode: 0644]
tools/xm-test/tests/block-integrity/Makefile.am